This section describes the following tasks:
Before enabling NFS access on a virtual server, ensure that an NIS domain is configured with the virtual server; see “Configuring an NIS-Domain Configuration” for instructions on setting up an NIS-domain configuration.
To enable NFS access on a virtual server, use the protocol nfs server new command. The command provides the following options and defaults:
Whether NFS access is enabled. The default is true.
The maximum number of RPCSEC_GSS authentication contexts, which are used by Kerberos. The default is 0 (zero). See RFC 2203 for information about RPCSEC_GSS contexts.
The amount of time an RPCSEC_GSS context is permitted to remain unused before it is deleted. The default is 0 (zero) seconds.
Whether NFS v2 is enabled. The default is true.
Whether NFS v3 is enabled. The default is true.
Whether NFS access is enabled over the UDP protocol. The default is true.
Whether NFS access is enabled over the TCP protocol. The default is true.
Whether the SpinAuth authentication method is enabled. The default is true. See XREF for more information about SpinAuth.
A list of default Windows users.
The following example enables NFS access on a virtual server named vs0. Default values are used for all parameters, and no default Windows users are specified.
node::>protocol nfs server new -vserver vs0 -access true -rpcsec-ctx-high 0 -rpcsec-ctx-idle 0 -v2-enable true -v3-enable true -udp-enable true -tcp-enable true -spinauth true
You can use the protocol nfs server kerberos-config modify command to enable or disable an NFS Kerberos configuration. An NFS Kerberos configuration is associated with both a virtual server and a virtual interface. If you enable an NFS Kerberos configuration, you must specify a service principal name (SPN) for the configuration. SPNs are in the form nfs/, where host_name@REALMhost_name is the fully qualified host name of the Kerberos server and REALM is the name of the Kerberos realm. Kerberos realm names must be in uppercase.
The following example enables an NFS Kerberos configuration on a virtual server named vs0 and a virtual interface named dataif1. The SPN is nfs/security.example.com@ENG.EXAMPLE.COM.
node::>protocol nfs server kerberos-config modify -vserver vs0 -vif dataif1 -kerberos enable -spn nfs/security.example.com@ENG.EXAMPLE.COM
The following example disables the NFS Kerberos configuration that was created in the previous example.
node::>protocol nfs server kerberos-config modify -vserver vs0 -vif dataif1 -kerberos disable
The protocol nfs server kerberos-config show command displays the following information about NFS Kerberos configurations:
Virtual server name
Virtual interface name
Virtual interface IP address
Whether Kerberos is enabled or disabled
Kerberos SPN
Numeric ID of the configuration
Other information is displayed in a detailed view and if other parameters are specified. See the reference page for the command for details.
The following example displays detailed information about the NFS Kerberos configuration that was disabled in the previous example:
node::>protocol nfs server kerberos-config show -vserver vs0 -vif dataif1Virtual Server ID: vs0 Virtual Interface: dataif1 VIF IP Address: 172.19.4.1 Kerberos Enabled: Disabled Service Principal Name: nfs/security.example.com@ENG.EXAMPLE.COM Numeric ID: 16
The protocol nfs server show command displays the following information about NFS configurations:
Virtual server name
Whether NFS access is enabled
Whether access to NFS v2 clients is enabled
Whether access to NFS v3 clients is enabled
Whether NFS access over UDP is enabled
Whether NFS access over TCP is enabled
Other information is displayed in a detailed view and if other parameters are specified. See the reference page for the command for details.
The following example displays information about all NFS configurations:
node::>protocol nfs server showVirtual General Enable Enable Enable Enable Server Access v2 v3 udp tcp vs0 true true true true true vs1 true false true false true
The protocol nfs server modify command enables you to modify the attributes of an NFS configuration. The following example modifies the NFS configuration on a virtual server named vs0 to disable SpinAuth:
node::>protocol nfs server modify -vserver vs0 -spinauth false
To delete a virtual server's NFS configuration, use the protocol nfs server delete command. The command does not delete the virtual server itself, just its ability to provide access to NFS clients.
If you delete a virtual server, as described in “Deleting a Virtual Server”, the virtual server's NFS configuration is automatically deleted. Any Windows-to-UNIX or UNIX-to-Windows name mappings defined for the virtual server are also deleted because they require both the CIFS and NFS servers.
The following example deletes the NFS configuration of a virtual server named vs1:
node::>protocol nfs server delete -vserver vs1